Service Availability

The Service Availability option is used for monitoring the availability of service for SBC devices that are deployed in the Live Platform topology. Devices are configured in clusters (up to three devices) and Live Platform monitors the entire cluster, calculating the aggregated availability of all devices based on connection time calculated over the polling interval (180 minutes). If connection cannot be established by Live Platform to all of the devices configured in the cluster, then Downtime is calculated as the ratio of the total number of minutes during the three hour interval that connection cannot be established to all devices in the cluster. For example, if there are two devices in the cluster, where both report 36 minutes of downtime, then the calculation is 36/180=0.2 (20% downtime), therefore the availability percentage is 80%.

You can initially configure the committed availability percentage value for the cluster according to the service agreement and then monitor the deviation from this value. For example if the Availability percentage is set to 90% and the reported data is calculated as 80%, then this differential may be taken into account for service billing.

These reports are used for Service-level and Customer-level Availability reporting. For Service level, separate clusters can be defined for example, for Direct Routing and Operator Connect. Disruptions to Service Availability can then be correlated to specific actions performed on the SBC device. For example, when uploading numbers to the Operator Connect service, numbers are uploaded simultaneously to multiple SBC devices, to the Microsoft platform and to the Live Platform UMP-365 device. Users can then correlate the downtime for SBC devices to validate connection issues when partial number upload responses are received on the Live Platform. Availability reports can be generated and exported as.CSV files.